ABI Layer 2: prove Alloy one-multiplicity constraint — flagship Idris2 proof#43
Merged
Merged
Conversation
Flagship semantic proof: an Alloy binary relation satisfies the `one` field multiplicity iff every live source maps to exactly one target (target-count = 1) — the OpenAPI "required, single-valued" property. Sound+complete Dec, certifier into the ABI Result codes proven sound, positive control + negative control (a one-source/two-target instance, the Alloy counterexample, is provably rejected). Verified with idris2 0.7.0 (build clean, zero warnings) + adversarial false-proof rejection. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6PSzJWpRxtzGDjUCEh7Mx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raises alloyiser's Idris2 ABI to Layer 2 with its first flagship semantic proof. alloyiser's headline is extracting formal models from API specs and verifying with Alloy; the most load-bearing thing an Alloy model expresses is a field multiplicity constraint. This proves the canonical
onemultiplicity: every live source maps to exactly one target (the OpenAPI "required, single-valued" property), with a one-source/two-target instance — exactly Alloy's counterexample for aonefield — provably rejected.Mirrors the estate flagship-proof pattern: relation model,
OneTargetFor/ConformsOnepropositions (uninhabited on count ≠ 1), sound+completeDec, certifier into the ABIResultcodes proven sound, positive + negative controls.Changes
src/interface/abi/Alloyiser/ABI/Semantics.idr—Relation/countTargets,OneTargetFor/ConformsOne,decConformsOne,certifyOneSound, and negative controls (badNotOneTarget,badNotConformsOne).alloyiser-abi.ipkg.RSR Quality Checklist
Required
As Applicable
Testing
Verified with Idris2 0.7.0:
idris2 --build alloyiser-abi.ipkg→ exit 0, zero warnings. Adversarial check: a deliberately-false proof (OneTargetFor 0 badRelation, where source 0 has two targets) was rejected.build/removed.🤖 Generated with Claude Code
https://claude.ai/code/session_01A6PSzJWpRxtzGDjUCEh7Mx
Generated by Claude Code